38 matches found
CVE-2025-21424
Memory corruption while calling the NPU driver APIs concurrently.
CVE-2025-21467
Memory corruption while reading the FW response from the shared queue.
CVE-2025-21468
Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer.
CVE-2024-53027
Transient DOS may occur while processing the country IE.
CVE-2024-49838
Information disclosure while parsing the OCI IE with invalid length.
CVE-2025-21453
Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur.
CVE-2024-53014
Memory corruption may occur while validating ports and channels in Audio driver.
CVE-2024-45553
Memory corruption can occur when process-specific maps are added to the global list. If a map is removed from the global list while another thread is using it for a process-specific task, issues may arise.
CVE-2024-49835
Memory corruption while reading secure file.
CVE-2024-49845
Memory corruption during the FRS UDS generation process.
CVE-2024-45562
Memory corruption during concurrent access to server info object due to unprotected critical field.
CVE-2024-49844
Memory corruption while triggering commands in the PlayReady Trusted application.
CVE-2024-45564
Memory corruption during concurrent access to server info object due to incorrect reference count update.
CVE-2024-49842
Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.
CVE-2024-38426
While processing the authentication message in UE, improper authentication may lead to information disclosure.
CVE-2024-45554
Memory corruption during concurrent SSR execution due to race condition on the global maps list.
CVE-2024-49841
Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling.
CVE-2024-53023
Memory corruption may occur while accessing a variable during extended back to back tests.
CVE-2024-45584
Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace.
CVE-2024-38420
Memory corruption while configuring a Hypervisor based input virtual device.
CVE-2024-43051
Information disclosure while deriving keys for a session for any Widevine use case.
CVE-2024-43057
Memory corruption while processing command in Glink linux.
CVE-2024-38414
Information disclosure while processing information on firmware image during core initialization.
CVE-2024-43056
Transient DOS during hypervisor virtual I/O operation in a virtual machine.
CVE-2024-45557
Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation.
CVE-2025-27061
Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmware.
CVE-2025-27042
Memory corruption while processing video packets received from video firmware.
CVE-2025-27043
Memory corruption while processing manipulated payload in video firmware.
CVE-2025-21450
Cryptographic issue occurs due to use of insecure connection method while downloading.
CVE-2025-21422
Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses.
CVE-2025-27052
Memory corruption while processing data packets in diag received from Unix clients.
CVE-2024-53009
Memory corruption while operating the mailbox in Automotive.
CVE-2025-21432
Memory corruption while retrieving the CBOR data from TA.
CVE-2025-21433
Transient DOS when importing a PKCS#8-encoded RSA private key with a zero-sized modulus.
CVE-2025-21446
Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests.
CVE-2025-21456
Memory corruption while processing IOCTL command when multiple threads are called to map/unmap buffer concurrently.
CVE-2025-21452
Transient DOS while processing a random-access response (RAR) with an invalid PDU length on LTE network.
CVE-2025-21458
Memory corruption when IOCTL interface is called to map and unmap buffers simultaneously.